Hi and welcome, @adhn said in General architectural questions: Should the new software completely be written and integrated into the Qt framework, i.e., frontend and backend? both is possible. You can write a non-Qt app / backend and slap a Qt frontend onto it... or you start with Qt from the beginning and throughout. The wireless communication with the sensors is critical to the disinfection process. Is it safe to integrate it into Qt as well, i.e. have one main entry point for the whole software, a.ka. a main.py file, which then starts the MQTT communication with the sensors, etc.? If you chose the latter approach and write a new "Qt app", you can also use Qt's other modules like QMqtt... this reduces the amount of 3rd party stuff needed for your app. Or, is it safe and more appropriate to directly display values on the screen, and only save the sensor data for each minute (as this is necessary for the reports)? This is also hard to tell from outstander's perspective. Both ways are possible. You can either display "live" data, as the interval (0.5 Hz) is far from being too frequent or you read the data from DB... Or... as I write this, I thought of buffering the data so you don't need to write to DB every 2s.... Store chunks of data, write to DB in even lower intervals and display the buffered live data that's on your RPi. @adhn said in General architectural questions: Since we do not have any high performance criteria (seconds are important, not milliseconds or mikroseconds), we would completely write it in Python with PySide6. This should be no issue I suppose. No usually not. The Python wrapper PySide is officially supported and migrates almost all features of Qt to Python... Don't know from the top of my head if this is the case for the QMQTT module... but should work. And if not, you can still use another MQTT implementation.

@DevWinDemon Everything you said above is wrong... There is no difference between Qt5 and Qt6 apps in the way they are deployed (or linked to Qt libs). A Qt5 app also does not work outside of the IDE environment and without its dependencies. Simple facts. @DevWinDemon said in Qt5 is better than Qt6: I ran it and it added libs to debug directory. But I want to share only .exe file without anything else Do what you want, but it doesn't work then :)) Because when I created dlls / exes in qt5 it could work without anything near, while officially installed qt 6 requires some libs Doubt. If the Qt5 app was built the same way, I guarantee you, it never worked as you describe. @DevWinDemon said in Qt5 is better than Qt6: App works inside the qt and I can it run from qt creator, but it requires libs if I wanna start app from explorer Yes, this is expected. @DevWinDemon said in Qt5 is better than Qt6: Why am I need it? qt 5 can create apps without any deploying, just with piece of code and "run" button Because it is how software development and programs work. What run button? The one in QtCreator?! There it is expected to work, because it's within the correct environment. The code that you write uses Qt libraries in your pre-set environment... when you compile your program and move the result somewhere else (either locally or send it to friends) the "dependencies" are not there anymore (or at least not in your app's search path / "sight") and it stops working. Nothing new, nothing wrong. Just how it works. If you don't want to do the required steps, don't blame Qt5 or Qt6 that it doesn't work.

AFAIK this should work but it will not be visible in Assets tab but rather in Components: [image: 4bac87b2-d7be-4ed2-96d3-7e5911dc4694.png] Moreover, I just tried that with your configuration and the file generated was not empty. Honestly, I do not know what might have happened, your best bet is creating a ticket and attaching the .fig and .qtbridge files.

I'm getting the following error when I run "Squish for Qt 9.0.0" squishrunner.exe : Found invalid metadata in lib ../dlls/qt/imageformats/qgif.dll: Invalid metadata version Using qtplugininfo I get the following metadata for the file: qtplugininfo .\imageformats\qgif.dll IID "org.qt-project.Qt.QImageIOHandlerFactoryInterface" Qt 6.8.0 (release) User Data: { "Keys": [ "gif" ], "MimeTypes": [ "image/gif" ] } Finally, the Squish installation buildinfo.txt file: Package Name: squish-9.0.0-qt68x-win64-msvc143 Internal Name: /home/autotest/public_html/binpackages/2025/02/28-1700/bin_package/9.0.0/qt/Teufelsbek-Qt6.8.0binary-TkNone-iOSNone-MSVC143x64-fcaab59 Git Branch: 9.0.0 Git Revision: 239e98e6029aa13633774415f0c38f3d47257f2d Python Version: default Patched: False Debug Build: False Debug Symbols: False Pure Qt4 Build: False Include IDE: True Python 2: S:/binPackage/Python/x64/2.7.10binary_ssl Python 3: S:/binPackage/Python/x64/3.10.6binary Tcl: S:/binPackage/tcl/x64/8.6.4 Perl: S:/binPackage/Perl/x64/5.34.0 Ruby: S:/binPackage/Ruby/x64/2.5.3 My build environment is Qt 6.8.2 and MSVC 2022 for a 64-bit target.

I already wrote to this e-mail by using the built-in function from youtestme - no answer yet. The result from the test is already there I am just waiting for the proctoring report. [image: 64449ca2-2b0f-4143-886d-e822cda62e62.png]

Solved by myself. I found "-utf-8" in two .conf files..

请问我的QT程序是关于连接远程数据库的，打包给其他的没有qt和数据库环境的电脑去连接数据库是可以的，但是放到同样的没有qt和数据库环境的机器配套的电脑连接远程数据库就显示driver not load，这个是因为什么，我个人的猜想是会不会是因为机器的电脑只有机器的配套软件而没有某些环境导致的？

Hi @RokeJulianLockhart, just some additional thoughts to consider... Kubuntu is an official "flavor" of Ubuntu. That is, its supported by Ubunutu, and has the same LTS and non-LTS releases Ubuntu has. KDE Neon is based-on an LTS Ubuntu, but is not supported by Ubuntu. It contains more recent KDE components, and is maintained (not sure about supported) by KDE devs. So there's definitely pro's and con's to both. But I'm sure both are good either way. I ask about Kubuntu explicitly because it's Qt-based, being the KDE Plasma variant, so I prefer it for verifying Qt bugs. While KDE is Qt-based, it actually uses Qt-derived libs, rather than Qt per se. So while it really doesn't matter, if you really like to use Qt on Ubuntu (as I do), then I can recommend Lubuntu, which is also an official Ubuntu flavour (supported by Ubuntu), but using the LXQt desktop by default instead. LXQt is a lightweight Qt-based desktop environment, so much more Qt-pure than KDE is (though again, it really doesn't matter). It's certainly not as feature rich as KDE, but then its without KDE's bloat too. LXQt suits my needs perfectly (by largely staying out of my way), but of course might not be right for you. Worth knowing about anyway. Cheers.